Real-time driver observation and progress monitoring

ABSTRACT

In an embodiment, movement-data is gathered with one or more sensors (e.g., accelerometers, GPS receivers, etc.) during a driver&#39;s driving session. A score may be calculated for the driving session, and the driver&#39;s progress is evaluated by a driver-evaluation system. A driving session report or graphical user-interface (GUI) is generated with a computer processor and displayed at a display device. The displayed report or GUI includes a graphic representing the driver&#39;s progress relative to historical data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of (i) U.S. application Ser. No.15/410,445, filed Jan. 19, 2017 and titled “Real-Time Driver Observationand Progress Monitoring,” which is a continuation of (ii) U.S.application Ser. No. 14/703,482, filed May 4, 2015 and titled “Real-TimeDriver Observation and Progress Monitoring,” the entire disclosures ofwhich are expressly incorporated herein by reference.

TECHNICAL FIELD

The present disclosure generally relates to a system and a method forobserving driving skills of a driver in real-time or near real-time,and, more particularly, to a computer system for collecting andanalyzing the real-time data to provide objective feedback regarding theprogression of the driver's skills.

BACKGROUND

An important goal of driving instruction is to teach drivers how todrive confidently and safely. In a typical scenario, a student-driverdrives a vehicle while a driving-instructor, generally sitting in thepassenger seat of the vehicle, observes the student-driver and providesverbal feedback to the student. The student typically relies on theverbal feedback from the driving-instructor to improve his or her skillas a driver. In some instances, the driving-instructor uses pen andpaper to make notes based on his or her observations.

SUMMARY

According to an embodiment of the techniques described in the presentdisclosure, progress of a driver's skill is evaluated based on datacollected from one or more sensors utilized to track a driver and/or thevehicle operated by the driver. A driver-evaluation system analyzes thecollected data and may provide a display to indicate how the driver'sskills are progressing.

BRIEF DESCRIPTION OF THE DRAWINGS

The figures described below depict various aspects of the system andmethods disclosed herein. It should be understood that each figuredepicts an embodiment of a particular aspect of the disclosed system andmethods, and that each of the figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingfigures, in which features depicted in multiple figures are designatedwith consistent reference numerals.

FIG. 1A illustrates an example trend graphic that may be displayed, viaa display device, to a user.

FIG. 1B illustrates a block diagram of an example driver-evaluationsystem according to an embodiment.

FIG. 2 illustrates an example method for evaluating driver progressaccording to an embodiment.

FIG. 3 illustrates a block diagram of an example driver-evaluationsystem according to an embodiment.

FIG. 4 illustrates an example graphical user-interface (GUI) that may bepresented by a display device according to an embodiment.

FIG. 5 illustrates example display devices according to variousembodiments

FIG. 6 illustrates a block diagram of an example mobile device accordingto an embodiment.

FIG. 7 is a flow diagram depicting an example method for displaying adriver evaluation report/GUI according to an embodiment.

FIG. 8 is a flow diagram depicting an example logging method accordingto an embodiment.

FIG. 9A is a flow diagram depicting an example logging method accordingto an embodiment.

FIG. 9B is a flow diagram depicting an example logging method accordingto an embodiment.

FIG. 10 illustrates an example method for calculating a driving scoreaccording to an embodiment.

FIG. 11 depicts an example method for calculating a driver scanningscore according to an embodiment.

DETAILED DESCRIPTION

Driver evaluation is subjective in nature. Current techniques for driverevaluation fail to effectively track the progress of a driver over timeor across multiple driving sessions, for example. In short, it isdifficult to objectively evaluate a driver's skill during a singledriving session, let alone to then compare such an evaluation to pastdriving sessions.

Even if the driver or the driving-instructor have a general sense thatthe driver has improved, the driver and driving-instructor may struggleto identify particular areas where the student-driver has improved orregressed. Without this critical information, the driving-instructorwill not be able effectively identify exercises or relevant feedback to(i) positively reinforce improving driver behavior or (ii) correctregressing driving behavior.

The systems and methods described herein enable objective evaluation ofdriving skill progression (or regression in some instances). Inparticular, the systems and methods may be implemented to objectivelyevaluate a driver's skill level and the extent of his or her progressrelative to previous driving sessions. As an example, the describedsystems and methods may be utilized to present visual feedbackindicating how a driver is progressing.

FIG. 1A illustrates an example trend graphic 110A (according to anembodiment) that may be displayed, via a display device, to a user.Generally speaking, the trend graphic 110A enables a user to gaugedriving skill progress. In particular, the trend graphic 110A providesinformation about a driver's skill relating to acceleration, braking,and cornering. In this example, the markers 111, 113, and 115 mark adriver's score for acceleration, braking, and cornering, respectively.The bars 117, 119, and 121 mark reference scores to which the driver'sscores are being compared. The reference scores may represent variousscores. For example, the reference scores may represent scores from thedriver's previous driving session. In an embodiment, the referencescores may represent the driver's average scores for multiple previousdriving sessions. In some embodiments, the reference scores mayrepresent class average scores (e.g., enabling a driving-instructor togauge a driver's progress relative to other students). In any event, thetrend graphic 110A enables user to gauge driving skill progress.

For example, by viewing the trend graphic 110A a user can observe thatthe marker 111 is positioned to the left of the end of the bar 117,enabling the user to determine the driver's acceleration score (and thusskill) has regressed. On the other hand, a user may observe that themarkers 113 and 115 are positioned to the right of the end of the bars119 and 121, enabling the user to learn that the driver's braking andcornering scores (and thus skills) have improved. Accordingly, a usercan quickly learn how a user is progressing or regressing with respectto his or her driving skills. In some embodiments, the trend graphic110A may be provided at a display device in real-time or near real-time,enabling a user to get instantaneous or near-instantaneous feedback. Theuser can utilize this feedback to quickly identify skills on which tofocus for improving overall driving behavior.

1. An Example Driver-Evaluation System

FIG. 1B illustrates a block diagram of an example driver-evaluationsystem 100 according to an embodiment. The driver-evaluation system 100may be utilized to present visual information to a user to indicatinghow a driver's skill or score is progressing. In an embodiment, thedriver-evaluation system 100 presents the trend graphic 110A describedwith reference to FIG. 1A.

In an embodiment, the driver-evaluation system 100 includes adriving-monitor system 30 communicatively connected to a display device40 via one or more links 105. The driver-evaluation system 100 may alsoinclude one or more sensors 61. For example, in an embodiment thedriving-monitor system 30 includes a sensor 61A. In some embodiments,the driving-monitor system 30 is communicatively connected to a sensor61B. The sensor 61B may be communicatively connected to thedriving-monitor system 30 via one or more links 107.

The one or more links 105 may be wired or wireless in nature. Similarly,the one or more links 107 may be wired or wireless in nature.

1.1. Example Sensors

In an embodiment, the driver-evaluation system 100 includes one or moresensors 61. For example, in an embodiment the driving-monitor system 30includes a sensor 61A. In an embodiment, the driver-evaluation system100 includes a sensor 61B communicatively connected to thedriving-monitor system 30 via one or more links 107.

Generally speaking, the sensors 61 detect movement and generate datarepresenting the detected movement (i.e., movement-data). In short, thesensors 61 are generally used to detect movement of a vehicle. Forexample, the sensors 61 may be installed or otherwise disposed at avehicle. Thus, in such an example, when the vehicle moves the sensors 61move. Accordingly, a sensor 61 may detect its own movement and maygenerate movement-data based on the detected movement. Because themovement of the sensor 61 corresponds to movement of the vehicle,movement of the vehicle can be determined from the movement-data.

The sensors 61 may be used to measure various aspects of or relating tomovement, such as position, speed, acceleration, and/or direction ofmovement. As an example, the sensors 61 may include one or more of: anaccelerometer, a GPS receiver, a speedometer, a compass, a gyroscope, acar brake sensor, and/or a tachometer. The sensors 61 may be sensors ofa mobile device (e.g., a phone or tablet), a vehicle computer, or anindependent electronic device (e.g., a dedicated GPS device).

In example operation, the sensor 61A detects movement and generatesmovement-data. The movement-data may be transmitted (e.g., via a systembus) to the memory 133 of the driving-monitor system 30.

As for the sensor 61B, in example operation the sensor 61B may detectmovement and generate movement-data. The movement-data may betransmitted to the driving-monitor system 30 via the one or more links107. Regardless of which sensor 61 generates the movement-data, thedriving-monitor system 30 may store received movement-data (e.g., at thememory 133) to a performance log 135.

1.2. An Example Driving-Monitor System

The driving-monitor system 30 is an electronic system or deviceincluding a processor 131 and a memory 133. In a typical example, theprocessor 131 and memory 133 are communicatively connected via a link,such as a system bus. The memory 133 may include persistent (e.g., ahard disk) and/or non-persistent (e.g., RAM) components.

The memory 133 stores one or more of: a performance log 135, a drivingscore 136, driving-scores 137, a progress score 138, and instructionsthat make up a progress module or application 139 for presenting adisplay (via the display device 40) to facilitate driver-progressmonitoring. In operation, the processor 131 fetches and executes theinstructions. In various implementations, the progress module 139 mayinclude compiled instructions, instructions that are interpreted atruntime, etc.

When executed by the processor 131, the progress module 139 causes thedriving-monitor system 30 to calculate a driving score 136 based on theperformance log 135. As noted above, the performance log 135 may includemovement-data representing movement detected by a sensor 61. Calculationof a driving score such as the driving score 136 is described in moredetail with reference to FIG. 10.

The progress module 139 also causes the driving-monitor system 30 tocompare the calculated driving score 136 to a previously calculateddriving score or group of scores 137. Depending on the implementation,the driving score 137 may be any one of: (i) a driving score calculatedfor the driver for a previous driving session; (ii) a group of scores,or a composite of previous scores, calculated for the driver; (iii) adriving score calculated for a previous driving session for a differentdriver; (iv) a group of scores, or a composite of previous scores,calculated for other drivers; or (v) some combination thereof. Utilizingdriving scores for other drivers may be beneficial for determining how adriving score for a particular driving session compares, for example, todriving scores calculated for other student-drivers in a class.

Based on the comparison of the calculated driving score 136 to thedriving score 137, the progress module 139 may cause the driving-monitorsystem 30 to determine a progress score 138. The progress score 138 maybe any record that indicates how the calculated driving score 136compares to the driving score 137. In particular, the progress score 138typically indicates an improvement or regression. The progress score 138may be a simple binary representation (e.g., 0=regression,1=improvement). In some instances, the progress score 138 may be morecomplex. For example, the progress score 138 may represent a percentimprovement or regression.

After the progress score 138 has been calculated, the progress module139 may cause the driving-monitor system 30 to transmit, via one or morelinks 105, video data or image data to the display device 40 to causethe display device 40 to present a trend graphic 110 that has beengenerated or retrieved from memory based on the calculated progressscore 138. In short, the trend graphic 110 indicates whether the drivingscore 136 represents an improvement or regression relative to a previousdriving score (or group of scores) 137. In an embodiment, the trendgraphic 110 may be similar, or even identical, to the trend graphic 110Ashown in FIG. 1A.

In an embodiment, the link 105 may be a wired or wireless link, and maybe connected to the driving-monitor system 30 via a video or graphicinterface (not shown) that is communicatively connected to a processor131 of the driving-monitor system 30. The driving-monitor system 30 maytransmit the video data or image data via such a graphic interface.

In some embodiments, the driving-monitor system 30 may transmit thevideo data or image data via a communication interface (not shown)connected to the processor 131. Such a communication interface maytransmit the video data or image data via a wired or wireless link.Further, the communication interface may transmit the video data orimage data via a network. For example, the communication interface maytransmit the video data or image data via a local area network (LAN) ora personal area network (PAN) to which the driving-monitor system 30 anddisplay device 40 are each coupled.

An example driving-monitor system 330 is described in detail withreference to FIG. 3.

1.3. An Example Display Device

The display device 40 may be any device configured to present visualinformation. Generally speaking, the display device 40 receives anelectrical input signal carrying video or image data. This video orimage data may represent a graphic or display generated or rendered bythe driving-monitor system 30. In example operation, the received videoor image data includes data representing a trend graphic 110. Uponreceiving the data, the display device 40 presents the trend graphic110. It will be noted that the trend graphic 110 may be presented as onegraphic or group of graphics which are part of a larger graphicaluser-interface (“GUI”) presented by the display device 40. Generallyspeaking, the trend graphic 110 is a graphic presented at the displaydevice 40 for purposes of informing a driver of his or her driving skillprogress.

FIGS. 4 and 5 illustrate example display devices and trend graphics thatmay be presented to a user.

1.4. Other Aspects

In an embodiment, one or more of the driving scores 137 are stored at amemory device not located at the driving-monitor system 30. For example,the driving scores 137 may be stored at a server (not shown). Thedriving-monitor system 30 may communicate with such a server via anetwork connection (e.g., to the Internet). In such an embodiment, thedriving-monitor system 30 may request a driving score 137, and maycompare a calculated driving score 136 to a received driving score 137.

Further, in some embodiments the driving-monitor system 30 may transmitthe calculated driving score 136 to a server for comparison to a drivingscore 137. In such embodiments, the driving-monitor system 30 maysubsequently receive a progress score 138, determined based on thecomparison, from the server. The driving-monitor system 30 may thentransmit video data or image data to the display device 40 to cause thedisplay device 40 to present a trend graphic 110 that has been generatedor retrieved from memory based on the received progress score 138.

In an embodiment, the driving-monitor system 30 transmits movement-datato a server for driving score calculation and/or for comparison to adriving score 137. In other words, a server may handle the driving scorecalculation and/or comparison to other driving scores 137. In such anembodiment, the driving-monitor system 30 may receive a progress score138 from the server.

In an embodiment, the driving-monitor system 30 may transmit video datato the display device 40 to cause the display device 40 to present thedriving score 136. In other words, the display device 40 may displayboth the trend graphic 110 and the driving score 136.

It will be noted that in some embodiments, the driving-monitor system 30is not connected to the sensor 61B. For example, the driving-monitorsystem 30 may utilize the sensor 61A, but not the 61B. In otherembodiments, the driving-monitor system 30 may utilize the 61B, but notthe sensor 61A. In some embodiments, the driving-monitor system 30utilizes both the sensor 61A and the sensor 61B.

2. An Example Method for Evaluating Driver Progress

FIG. 2 illustrates an example method 200 for evaluating driver progressaccording to an embodiment. The method 200 may be implemented by thedriver-evaluation system 100 shown in FIG. 1B. The method 200 may besaved as a set of instructions, routines, programs, or modules atcomputer readable media found, for example, in memory devices accessibleby the driver-evaluation system 100. For example, some or all of themethod 200 may be saved as the progress module 139 described withreference to FIG. 1B. While the method 200 is described with referenceto the driver-evaluation system 100 and the driving-monitor system 30shown in FIG. 1B, the method 200 may be implemented according to otherembodiments not depicted in FIG. 1B. For example, the method 200 mayalso be implemented, at least in part, by the driving-monitor system 330shown in FIG. 3.

2.1. Driver Tracking

The method 20 begins when a driver's actions are tracked (block 211).Tracking a driver's action may include tracking movement of a vehicle(e.g., via one of the sensors 61 described with reference to FIG. 1B)and/or tracking the driver himself or herself (e.g., via a camera).

2.2. Driving Score Generation

After tracking the driver, a driving score 136 is calculated based onthe tracked actions (block 213). The driving score 136 may be calculatedby the driving-monitor system 30 shown in FIG. 1B based on data in theperformance log 135 shown in FIG. 1B. In particular, the driving scoremay be calculated based on movement-data generated, e.g., by one of thesensors 61 shown in FIG. 1B. An example method for calculating a drivingscore is described in more detail with reference to FIG. 10.

2.3. Progress Determination

After a driving score 136 has been calculated, the calculated drivingscore 136 may be compared to one or more other driving scores (block215). The comparison may be used to calculate a progress score 138. Theprogress score 138 may be any record that indicates how the calculateddriving score compares to the calculated driving score. In particular,the progress score 138 typically indicates an improvement or regression.The progress score 138 may be a simple binary representation (e.g.,0=regression, 1=improvement). For example, if the calculated drivingscore is 78 and the comparison score is 75, the progress score 138 maybe 1 (e.g., indicating an improvement). Alternatively, if the comparisonscore is 80, the progress score 138 may be 0 (e.g., indicatingregression).

In some instances, the progress score 138 may be more complex. Forexample, the progress score 138 may be ternary in nature (i.e., threepossible values). As an example, the progress score 138 may be −1 (e.g.,indicating regression), 0 (e.g., indicating stasis or lack of change inthe score), or 1 (e.g., indicating improvement). In some instances, theprogress score 138 may be a percent. With reference to the previousexample, if the driving score is 78 and the comparison score is 75, theprogress score 138 may be 4% (i.e., the driving score is a 4%improvement over the previous score). Regardless of the exact nature ofthe progress score 138, it is possible to determine whether a drivingscore represents an improvement or not.

2.4. Progress Notification

After the calculated driving score 136 has been compared to one or moreother driving scores 137, an indication of the driver's progress may beprovided (block 217). In a typical example, the display device 40 (shownin FIG. 1B) presents the indication. Examples of such an indicationinclude the trend graphic 110 (shown in FIG. 1B) and the trend graphics410 (shown in FIG. 4). In short, the indication is a visualrepresentation of the progress score 138 determined by comparing thecalculated driving score 136 to a previous driving skill score 137.

3. An Example Driving-Monitor System

FIG. 3 illustrates a block diagram of an example driver-evaluationsystem 300 according to an embodiment. The driver-evaluation system 300is a computer system for performing at least one of: driver tracking(e.g., see block 211 shown in FIG. 2), driving score calculation (e.g.,see block 213 shown in FIG. 2), progress determination (e.g., see block215 shown in FIG. 2), and/or progress display (e.g., see block 217 shownin FIG. 2). The driver-evaluation system 300 may be similar in nature tothe driver-evaluation system 100, capable of performing similarfunctions and interfacing with similar systems. In particular, thedriver-evaluation system 300 may include a driving-monitor system 330,which may be similar to the driving-monitor system 30. In an embodiment,the driving-monitor system 330 may include front-end components 311and/or back-end components 313. The driving-monitor system 330 mayinclude one or more of: a mobile device 325, an on-board computer 329,and a server 351.

3.1. Example Communications Between the Driving-Monitor System 330 andOther Devices/Systems

The driver-evaluation system 300 may include a display device 40 (shownin FIG. 1B). For example, the mobile device 325 of the driving-monitorsystem 330 may be coupled to an integrated display (not shown) thatshares a housing with other components of the mobile device 325. Asanother example, the on-board computer 329 of the driving-monitor system330 may be coupled to a display device (not shown) installed in the dashof the vehicle 323. In an embodiment, the display device 40 is a displayindependent of the mobile device 325 and the on-board computer 329. Forexample, the display device 40 may be a display of a tablet or computernot shown in FIG. 3.

Further, the driver-evaluation system 300 may include a sensor 61 (shownin FIG. 1B). For example, the mobile device 325 or the on-board computer329 may include a sensor 61. In some instances, the driving-monitorsystem 330 may communicate with a sensor 61 (e.g., via the mobile device325 or the on-board computer 329) that is installed or otherwisedisposed in the vehicle (e.g., via a wired or wireless link). Forexample, the driving-monitor system 330 may communicate with a dedicateGPS receiver (not shown) disposed in the vehicle (e.g., in the interior,such as in the cabin, trunk, or engine compartment, or on the exteriorof the vehicle).

3.2. Example Components of the Driving-Monitor System 330

The high-level architecture of the driving-monitor system 330 includesboth hardware and software applications, as well as various datacommunication channels or links for sending and receiving data betweenthe various hardware and software components. The driving-monitor system330 may be roughly divided into front-end components 311 and back-endcomponents 313. The front-end 311 may be communicatively coupled to theback-end 313 via the network 341.

The network 341 may be a proprietary network, a secure public internet,a virtual private network or some other type of network, such asdedicated access lines, plain ordinary telephone lines, satellite links,combinations of these, etc. Where the network 341 comprises theInternet, data communications may take place over the network 341 via anInternet communication protocol.

-   -   3.2(A) The Front-End Components 311

The front-end components 311 of the driving-monitor system 330 may beinstalled or located at a vehicle 323, which may be driven by a driver321. The front-end 311 includes a mobile device 325 and/or an on-boardcomputer 329. In some embodiments the front-end 311 may include atactile alert system 335 and/or one or more speakers 337. The front-endcomponents 311 may be communicatively connected to the network 341 viathe link 327 and/or the link 333. The links 327 and 333 may each bewireless or wired, depending on the embodiment.

The mobile device 325 is an electronic device that may be permanently orremovably installed in the vehicle 323 (e.g., a car, truck, etc.). Themobile device 325 may be a general-use mobile personal computer,cellular phone, smart phone, tablet computer, other wearable computer(e.g., a watch, glasses, etc.), a dedicated driving-monitor computer,etc.

In an embodiment, the mobile device 325 may be communicatively connectedto the network 341 via the link 327. The mobile device 325 may include acommunication interface (not shown) for sending and receiving data viathe link 327. In some embodiments, the mobile device 325 is notconnected to the network 341

The on-board computer 329 is an electronic device that may bepermanently or temporarily installed in the vehicle 323. The on-boardcomputer 329 may be a general-use on-board computer capable ofperforming many functions relating to vehicle operation or a dedicateddriver's education evaluation computer. The on-board computer 329 may beinstalled by the manufacturer of the vehicle 323 or as an aftermarketmodification to the vehicle 323.

The on-board computer 329 may be communicatively connected to thenetwork 341 via the link 333. The on-board computer 329 may include acommunication interface (not shown) for sending and receiving data viathe link 333. In some embodiments, the on-board computer 329 is notconnected to the network 341. The on-board computer 329 may becommunicatively connected to various sensors in the vehicle 323 (e.g., abraking sensor, a speedometer, a tachometer, etc.) and/or may interfacewith various external output devices in the vehicle 323 such the tactilealert system 335, one or more speakers 337, one or more displays (notshown), etc.

In some embodiments, the mobile device 325 may be communicativelyconnected to the on-board computer 329 via the link 331. Such aconnection may be beneficial where the mobile device 325 and theon-board computer 329 each perform one or more functions of thedriving-monitor system 330. The link 331 may be a wired or wirelessconnection. In some embodiments, the mobile device 325 is notcommunicatively connected to the on-board computer 329. In someembodiments, the mobile device 325 and/or on-board computer 329 may be athin-client device which outsources some or most processing to theserver 351.

-   -   3.2(B) The Back-End Components 313

The back-end components 313 may be installed or otherwise disposed at aremote location relative to the vehicle 323 (e.g., at a data center).The back-end 313 may include a server 351, which may include one or morecomputer processors adapted and configured to execute various softwareapplications and components of the driving-monitor system 330, inaddition to other software applications. The back-end 313 may becommunicatively connected to the network 341 via a link 343, which maybe wireless or wired.

The server 351 may include a controller 353 and/or a database 355. Thecontroller 353 may include a processor 361 communicatively connected,via a link 367, to one or more of: a memory 363 (e.g., program memory),a memory 365 (e.g., RAM), and an I/O interface 369. In an embodiment,the memory 363 stores computer-readable instructions that when executedby the processor 361 cause the server 351 to implement a serverapplication 371 and/or a web server 373. The instructions for the serverapplication 371 may cause the server 351 to implement, at least in part,the methods described herein. That is, the server application 371 maycause the server 351 to calculate a driving score, compare a drivingscore to other driving scores, determine a progress score, and/orgenerate or select a trend graphic 110 (shown in FIG. 1B). In someembodiments the methods described herein are implemented without theserver 351.

The controller 353 may be communicatively connected to the network 341via a link 343 and the I/O circuit 369. Further, the controller 353 maybe communicatively connected to the database 355 via a link 367.

3.3. Example Operation of the Driving-Monitor System 330

In example operation, one or more drivers 321 may operate the vehicle323. While shown in a slightly reclined sitting position, those ofordinary skill in the art will appreciate that the driver 321 may besituated in any number of ways (e.g., reclining at a different angle,standing, etc.) and operating the vehicle using controls other than thesteering wheel and pedals shown in FIG. 3 (e.g., one or more sticks,yokes, levers, etc.).

-   -   3.3(A) Driver Tracking

A sensor 61 (shown in FIG. 1B) may detect movement of the vehicle 323while the driver 321 operates the vehicle 323. The sensor 61 may thentransmit movement-data, representing the detected movement, to thedriving-monitor system 330.

For example, the movement-data may be transmitted to the mobile device325 or to the on-board computer 329, depending on the embodiment. In anembodiment, the sensor 61 may be a sensor of driving-monitor system 330.For example, the sensor 61 may be a sensor of the mobile device 325 orof the on-board computer 329. In some embodiments, the sensor 61 is asensor for a device that is independent of the mobile device 325 andon-board computer 329.

-   -   3.3(B) Driving Score Calculation

After the driving-monitor system 330 receives the movement-data (e.g.,at the mobile device 325), the driving-monitor system 330 may calculatea driving score based on the movement-data. For example, the mobiledevice 325 or on-board computer 329 may calculate a driving score basedon the movement-data. The mobile device 325 or on-board computer 329 mayretrieve the movement-data from a performance log 135 (shown in FIG.1B), which may be stored at the mobile device 325, the on-board computer329, or the server 351.

Alternatively, the server 351 may calculate the driving score. In suchan embodiment, either the mobile device 325 or the on-board computer 329may transmit the movement-data to the server 351. The server 351 maythen calculate the driving score based on the received movement-data. Insome embodiments, server 351 may transmit the calculated driving scoreto the mobile device 325 or the on-board computer 329.

-   -   3.3(C) Progress Determination

After a driving score is calculated, the driving-monitor system 330 maycompare the calculated driving score to other previously calculateddriving scores (which may be stored to memory at the mobile device 325,on-board computer 329, or server 351, depending on the embodiment). Thecomparison may be performed, e.g., by the mobile device 325, theon-board computer 329 or the server 351, depending on the embodiment.

In an embodiment, whichever of the mobile device 325, on-board computer329, and server 351 performs the comparison may notify one or more ofthe other systems of the results of the comparison. For example, theserver 351 may perform the comparison and send a signal to the mobiledevice 325 and/or on-board computer 329 to notify the mobile device 325and/or on-board computer 329 of the comparison results. In anembodiment, the server 351 calculates a progress score based on thecomparison and sends the calculated progress score to the mobile device325 and/or on-board computer 329 (via the network 341).

In an embodiment, the mobile device 325 performs the comparison andsends a signal to the on-board computer 329 and/or server 351 to notifythe computer 329 and/or server 351 of the comparison results. Forexample, the mobile device 325 may send a progress score, calculatedbased on the comparison, to the server 351. The server 351 may updaterecords stored at the database 355 based on the received progress score.

-   -   3.3(D) Trend/Progress Display

Based on the results of the comparison, the driving-monitor system 330generates or selects a graphic (e.g., trend graphic 110 shown in FIG. 1)for indicating whether the calculated driving score represents animprovement or regression relative to a previous driving score to whichit was compared. The driving-monitor system 330 then transmits datarepresenting the graphic to a display device 40, where the graphic isdisplayed. The display device 40 may be a display screen for the mobiledevice 325, a display screen for a second mobile device 325, a displaycoupled to the on-board computer 329, or a display for another device.

In an embodiment, the mobile device 325 generates or selects thegraphic. Further, the display device 40 may be a display screen of themobile device 325. Accordingly, the display device 40 may receive thedata representing the graphic via a system bus of the mobile device 325.Similarly, in some embodiments the graphic may be selected and displayedby the on-board computer 329.

In some embodiments, the graphic may be selected by one of the mobiledevice 325 or on-board computer 329, and the data representing thegraphic may be transmitted to the other of the mobile device 325 andon-board computer 329 via the link 331 or network 341.

3.4. Other Aspects of the Driving-Monitor System 330

Depending on the embodiment, the driving-monitor system 330 may havevarious configurations. For example, in an embodiment thedriving-monitor system 330 may include only the front-end 311. In otherwords, the functionality of the driving-monitor system 330 may beprovided entirely by the front-end 311 in some embodiments. Further, amobile device 325 may perform all of the processing associated with datacollection and driver tracking, driving score calculation, progressdetermination, and progress display. In an embodiment, the on-boardcomputer 329 may similarly perform all of the processing. As such, thedriving-monitor system 330 may be a “stand-alone” system, neithersending nor receiving information over the network 341.

In some embodiments, the driving-monitor system 330 may be a distributedsystem where the functionality of the driving-monitor system 330 isdivided between the front-end 311 and back-end 313.

More generally speaking, although the driving-monitor system 330 isshown to include one server 351, one mobile device 325, and one on-boardcomputer 329, it should be understood that different numbers of servers351, devices 325, and on-board computers 329 may be utilized. Forexample, the system 329 may include a plurality of servers 351 and/or aplurality of devices 325, all of which may be interconnected via thenetwork 341.

-   -   3.4(A) Other Aspects of the Front-End 311

Further, the front-end 311 may have various configurations depending onthe embodiment. For example, in an embodiment the front-end 311 mayinclude only one of the mobile device 325 and the on-board computer 329.In other words, most or all of the functions performed by the front-end311 may be performed by only one of the mobile device 325 and on-boardcomputer 329. Thus, in some embodiments the mobile device 325 mayperform the various functions described herein alone, and the on-boardcomputer 329 need not be present. Similarly, in some embodiments theon-board computer 329 may perform the various functions described hereinalone, and the mobile device 325 need not be present.

Moreover, in some embodiments the front-end 311 includes both the mobiledevice 325 and the on-board computer 329. In such embodiments, thefunctions performed by the front-end 311 may be divided between themobile device 325 and the on-board computer 329. In other words, themobile device 325 and on-board computer 329 may operate in conjunctionto provide the functionality of the front-end 311 (and in some cases,the functionality of the driving-monitor system 330). Similarly, thefunctionality of the driving-monitor system 330 may be divided betweenthe front-end 311 and the back-end 313.

In an embodiment, the driver 321 may receive tactile alerts presentedvia the tactile alert system 335. Such alerts may be presented oncommand from the mobile device 335 and/or the on-board computer on-boardcomputer 329.

-   -   3.4(B) Other Aspects of the Back-End 313

The processing performed by the one or more servers 351 may bedistributed among a plurality of servers 351 in an arrangement referredto as “cloud computing.” This configuration may provide severaladvantages, such as, for example, enabling near real-time uploads anddownloads of information as well as periodic uploads and downloads ofinformation. This may provide for a thin-client embodiment of the mobiledevice 325 and/or on-board computer 329 discussed herein as well as aprimary backup of some or all of the data gathered by the mobile device325 and/or on-board computer 329.

Moreover, it should be noted that while not shown, additional databasesmay be linked to the controller 353 in a known manner. While shown as asingle block in FIG. 3, it will be appreciated that the serverapplication 371 may include a number of different programs, modules,routines, and sub-routines that may collectively cause the server 351 toimplement the server application 371. While the instructions for theserver application 371 and web server 373 are shown as stored in thememory 363, the instructions may additionally or alternatively be storedin the database 355 and/or memory 365. It should be appreciated thatalthough only one processor/microprocessor 361 is shown, the controller353 may include multiple processors/microprocessors 361.

Additionally, the memories 363 and 365 may be implemented in variousforms. For example, the memories 363 and 365 may be implemented assemiconductor memories, magnetically readable memories, and/or opticallyreadable memories. Moreover, the controller 353 may include additionalmemory devices not shown in FIG. 3.

In example operation, the database 355 stores data related to theoperation of the driving-monitor system 330. Such data might include,for example, data collected by a mobile device 325 and/or on-boardcomputer 329 pertaining to the driving-monitor system 330 and uploadedto the server 355, such as images, sensor inputs, data analyzedaccording to the methods discussed below, or other kinds of data. Theserver 351 may access data stored in the database 335 when executingvarious functions and tasks associated with the operation of thedriving-monitor system 330. The data in the database 355 may be storedat one or more memory devices communicatively connected to thecontroller 353 (e.g., via the link 357). In an embodiment, data in thedatabase 355 is stored at the memory 363 and/or the memory 365.

Although the I/O circuit 369 is shown as a single block, it should beappreciated that the I/O circuit 369 may include a number of differenttypes of I/O circuits.

4. An Example Graphical User Interface (“GUI”)

FIG. 4 illustrates an example GUI 411 that may be presented by a displaydevice 440 according to an embodiment. Generally speaking, the displaydevice 440 presents a GUI 411 including a trend graphic (e.g., trendgraphic 110 shown in FIG. 1B) that has been selected or generated (e.g.,by the driving-monitor system 30 shown in FIG. 1B) based on a progressscore (e.g., progress score 138 shown in FIG. 1B) and/or results from acomparison between a calculated driving score (e.g., driving score 136shown in FIG. 1B) and one or more previously calculated driving scores(e.g., driving scores 137 shown in FIG. 1B). FIG. 2 illustrates anexample method 200 that may be implemented to select or generate such atrend graphic.

4.1. The Display Device 440

In an embodiment, the display device 440 may be part of thedriver-evaluation system 100 shown in FIG. 1B, and may be utilized inplace of or in addition to the display device 40 shown in FIG. 1B.Similarly, the display device 440 may be part of the driver-evaluationsystem 300 shown in FIG. 3, and may, e.g., present a display based ondata received from the driving-monitor system 330 shown in FIG. 3.Generally speaking, the display device 440 is similar in nature to thedisplay device 40, capable of performing similar functions andinterfacing with similar systems.

In an embodiment, the display device 440 may present the trend graphic110 shown in FIG. 1B. More generally, the display device 440 may presentvisual information based on video data or image data received from adriving-monitor system such as the driving-monitor system 30 shown inFIG. 1B or the driving-monitor system 330 shown in FIG. 3. In someembodiments, the display device 440 may present visual information basedon video data or image data received from the mobile device 325 or fromthe on-board computer 329 shown in FIG. 3.

4.2. The GUI 411

The display device 440 may present, via the GUI 411, a number ofgraphics and/or input elements. For example, the GUI 411 may include:trend graphic 110A; a trend graphic 410A; a trend graphic 410B; adriver-name graphic 413; a input element 415; a session statisticsgraphic 417; a input elements 419; and/or score graphic 421.

4.3. The Trend Graphic 110A

The trend graphic 110A includes driving scores for three sub-skills(i.e., acceleration, braking, and cornering). The trend graphic 110Aalso includes graphs illustrating how each of the sub-skill compares toprevious sub-skill scores. In particular, the trend graphic 110Aindicates that the acceleration score has regressed, while the brakingand cornering scores have improved. The trend graphic 110A is describedin detail with reference to FIG. 1A.

4.4. The Trend Graphic 410A

The trend graphic 410A is an example trend graphic that may be displayedby the display device 440. In the shown example, the trend graphic 410Ais an arrow. The upward facing arrow indicates that the calculateddriving score is an improvement (relative to one or more previousscores). When the calculated driving score represents a regression, thetrend graphic 410A may alternatively be a downward facing arrow. Inshort, the trend graphic 410A is an example graphic that may indicateone of two statuses: improvement or regression.

4.5. The Trend Graphic 410B

The trend graphic 410B includes text. More particularly, the trendgraphic 410B includes numbers quantifying how the driving score istrending. In combination with the score graphic 421, a user can quicklyidentify how his or her most recent score is trending relative tohistorical data. That is, the user can quickly determine how his or herscore compares to his or her previous score, best score, and/or worstscore. Depending on the embodiment, the trend graphic 410A may representa trend relative to any of the aforementioned scores.

4.6. The Driver-Name Graphic 413

The driver-name graphic 413 identifies the current driver participatingin the driving session. For example, the driver-name graphic 413 mayidentify the driver 321 shown in FIG. 3. The driver-name graphic 413 maybe useful, e.g., to a driving-instructor teaching or evaluating multiplestudents. In other words, the driver-name graphic 413 enables a user toview the display device 440 and determine the identity of a driver whoreceived the driving score shown by the score graphic 421.

4.7. The Input Element 415

The input element 415 is a touch graphic that enables a user (e.g., adriving-instructor) to change drivers. This may be useful where adriving-instructor is teaching or evaluating multiple students.

4.8. The Session Statistics Graphic 417

The session statistics graphic 417 includes statistics about thedriver's most recent driving session, such as the driving duration, thenumber of trips the driver has taken, and the distance of the mostrecent driving session.

4.9. Input Elements 419

The input elements 419 enable a user to interact with the GUI 411. Inparticular, a user may interact with (e.g., via touch) one of the inputelements 419 to begin recording a driving session. Such an action causesthe driver-evaluation system 100 to begin tracking the driver for aparticular driving session. When the driving session has finished, auser may interact with one of the input elements 419 again to stoprecording. Another one of the input elements 419 enables a user tocompare his driving session to other driving sessions. Finally one ofthe input elements 419 enables a driver to share his driving tripinformation via a social network or email.

4.10. The Score Graphic 421

The score graphic 421 displays the driving score (e.g., driving score136 shown in FIG. 1B) calculated for the most recent driving session.

4.11. Other Aspects

In an embodiment, the GUI 411 may not include input elements. Forexample, the display device 440 may be a display screen that is notconfigured for user interaction. In such an example, the display device40 may present the GUI 411 without interactive elements such as theinput elements 415 and 419.

5. Example Display Devices

FIG. 5 illustrates example display devices 540 according to variousembodiments. Each of the display devices 540 may be part of thedriver-evaluation system 100 shown in FIG. 1B, and may be utilized inplace of or in addition to the display device 40 shown in FIG. 1B. Eachdisplay device 540 may be similar in nature to the display device 40,capable of performing similar functions and interfacing with similarsystems.

In an embodiment, the display devices 540 may present the trend graphic110 shown in FIG. 1B. More generally, the display devices 540 maypresent visual information based on video data or image data receivedfrom a driving-monitor system such as the driving-monitor system 30shown in FIG. 1B or the driving-monitor system 330 shown in FIG. 3. Insome embodiments, the display device 540 may present visual informationbased on video data or image data received from the mobile device 325 orfrom the on-board computer 329 shown in FIG. 3.

The display device 540A is a screen of a mobile phone 511. The displaydevice 540B is an in-dash display for a vehicle 513. The display device540C is a projector for a projector device 515. The display device 540Dis a heads-up display (HUD) for a vehicle 517. The display device 540Eis a screen for a tablet 519. The display device 540F is a screen for acomputer 521.

6. An Example Mobile Device

FIG. 6 illustrates a block diagram of an example mobile device 325according to an embodiment. The mobile device 325 may be used for:driver tracking (e.g., see block 211 shown in FIG. 2), driving scorecalculation (e.g., see block 213 shown in FIG. 2), progressdetermination (e.g., see block 215 shown in FIG. 2), and/or progressdisplay (e.g., see block 217 shown in FIG. 2). In an embodiment, themobile device 325 performs one or more of these functions independently.In some embodiments, the mobile device 325 interacts with a on-boardcomputer 329 (shown in FIG. 3) and/or a server 351 (shown in FIG. 3) toprovide one or more of these functions.

The mobile device 325 and server 351 may be communicatively connectedvia a network 341. The server 351 may be installed or otherwise disposedat a remote location relative to the mobile device 325 (e.g., at a datacenter). The network 341 may be any suitable network. It will beunderstood that the on-board computer 329 shown in FIG. 3 may includemany of the same components as those included in the mobile device 325,and may provide similar functionality (as noted with reference to FIG.3).

In an embodiment, the mobile device 325 includes a controller 611. Inembodiment, the mobile device 325 may include only the controller 611.Further, in some embodiments the driving-monitor system 330 shown inFIG. 3 may include only the controller 611. In other words, thefunctionality of the driving-monitor system 330 may be provided entirelyby the controller 611 in some embodiments.

In some embodiments, the mobile device 325 may include one or moresensors 61 (e.g., a front image capture device 621, a GPS 623, backimage capture device 627, and/or accelerometer array 629) and/or adisplay device 40. In an embodiment, the mobile device 325 may include acommunication interface 625, a speaker 631, and/or a user-input device633. In some embodiments, the on-board computer 329 may include at leastone of: the controller 611, one or more sensors 61, the display device40, the communication unit 625, the speaker 631, and/or the user-inputdevice 633.

The front and back image capture devices 621 and 627 may be built-incameras within the mobile device 325 and/or may be peripheral cameras,such as webcams, cameras installed inside the vehicle 323, camerasinstalled outside the vehicle 323, etc., that are communicativelycoupled with the mobile device 325. The front image capture device 621may be oriented toward the driver 321 to observe the driver 321 asdescribed below. The back image capture device 627 may be orientedtoward the front of the vehicle 323 to observe the road, lane markings,and/or other objects in front of the vehicle 323. Some embodiments mayhave both a front image capture device 621 and a back image capturedevice 627, but other embodiments may have only one or the other.Further, either or both of the front image capture device 621 and backimage capture device 627 may include an infrared illuminator 621 i, 627i, respectively, to facilitate low light and/or night image capturing.Such an infrared illuminator 621 i, 627 i may be automatically activatedwhen light is insufficient for image capturing.

The GPS unit 623 may use “Assisted GPS” (A-GPS), satellite GPS, or anyother suitable global positioning protocol (e.g., the GLONASS systemoperated by the Russian government) or system that locates the positionof the mobile device 325. For example, A-GPS utilizes terrestrial cellphone towers or Wi-Fi hotspots (e.g., wireless router points) to moreaccurately and more quickly determine location of the mobile device 325,while satellite GPS generally are more useful in more remote regionsthat lack cell towers or Wi-Fi hotspots.

The accelerometer array 629 may be one or more accelerometers positionedto determine the force and direction of movements of the mobile device325. In some embodiments, the accelerometer array 629 may include anX-axis accelerometer 629 x, a Y-axis accelerometer 629 y, and a Z-axisaccelerometer 629 z to measure the force and direction of movement ineach dimension respectively. It will be appreciated by those of ordinaryskill in the art that a three dimensional vector describing a movementof the mobile device 325 through three dimensional space can beestablished by combining the outputs of the X-axis, Y-axis, and Z-axisaccelerometers 629 x, y, z using known methods. The GPS unit 623, thefront image capture device 621, the back image capture device 627, andaccelerometer array 629 may be referred to collectively as the “sensors”of the mobile device 325. Of course, it will be appreciated thatadditional GPS units 623, front image capture devices 621, back imagecapture devices 627, and/or accelerometer arrays 629 may be added to themobile device 325 (and/or on-board computer 329).

The mobile device 325 may include a display interface for providinggraphical data (e.g., image or video data) to a display device such asthe display device 40. In an embodiment, the mobile device 325 does notinclude the display device 40.

The communication unit 625 may communicate with the server 351 via anysuitable wireless communication protocol network, such as a wirelesstelephony network (e.g., GSM, CDMA, LTE, etc.), a Wi-Fi network (802.11standards), a WiMAX network, a Bluetooth network, etc. The communicationinterface 625 may also be capable of communicating using a near fieldcommunication standard (e.g., ISO/IEC 18092, standards provided by theNFC Forum, etc.). Further, the communication interface 625 may use awired connection to the server 351.

In an embodiment, the speaker 631 may be used to provide audio feedbackin addition to or instead of the visual feedback provided via thedisplay device 40. For example, the speaker 631 may provide audio in theform of natural language communication to notify a user of his or herdriving skill progress, driving score, etc. The natural languagecommunication may be in English, Spanish, or any other suitablelanguage. In some embodiments, the speaker 631 may produce anon-linguistic sound to notify a user of improvement or regression.

The user-input device 633 may include a “soft” keyboard that isdisplayed on the display 40 of the mobile device 325, an externalhardware keyboard communicating via a wired or a wireless connection(e.g., a Bluetooth keyboard), an external mouse, or any other suitableuser-input device. The user-input device 633 may also include amicrophone capable of receiving user voice input.

6.1. Controller 611

The controller 611 includes a processor 641 communicatively connected,via a link 649, to one or more of: a memory 643 (e.g., a random-accessmemory), a memory 645 (e.g., a program memory), and/or an I/O interface647. The link 649 may be a system bus. The program memory 645 includesan operating system 661, a data storage 663, a plurality of softwareapplications 665, and a plurality of software routines 667.

As discussed with reference to the controller 611, it should beappreciated that although FIG. 6 depicts only oneprocessor/microprocessor 641, the controller 611 may include multipleprocessors/microprocessors 641. Similarly, the memory of the controller611 may include multiple RAMs 643 and/or multiple program memories 645.Although FIG. 6 depicts the I/O circuit 647 as a single block, the I/Ocircuit 647 may include a number of different types of I/O circuits. Thecontroller 611 may implement the memory 643 and/or memory 645 assemiconductor memories, magnetically readable memories, and/or opticallyreadable memories, for example.

The memory 645 may include data and/or instructions. For example, thememory 645 may include data and/or instructions for an OS 661, a datastorage 663, software applications 665, software routines 667, clientapplication 669, image capture routine 671, browser 673, accelerometerroutine 675, and/or a browser 677.

The operating system 661, for example, may include one of a plurality ofmobile platforms such as the iOS®, Android™, Palm® webOS, Windows®Mobile/Phone, BlackBerry® OS, or Symbian® OS mobile technologyplatforms, developed by Apple Inc., Google Inc., Palm Inc. (nowHewlett-Packard Company), Microsoft Corporation, Research in Motion(RIM), and Nokia, respectively.

The data storage 663 may include data such as user profiles andpreferences, application data for the plurality of applications 665,routine data for the plurality of routines 667, and other data necessaryto interact with the server 613 through the digital network 615. In someembodiments, the controller 204 may also include, or otherwise becommunicatively connected to, other data storage mechanisms (e.g., oneor more hard disk drives, optical storage drives, solid state storagedevices, etc.) that reside within the mobile device 325 and/or on-boardcomputer 329.

The one or more processors 641 may be adapted and configured to executeany of one or more of the plurality of software applications 665 and/orany one or more of the plurality of software routines 667 residing inthe memory 645, in addition to other software applications. One of theplurality of applications 665 may be a client application 669 that maybe implemented as a series of machine-readable instructions forperforming the various tasks associated with implementing thedriver-evaluation system 100 as well as receiving information at,displaying information on, and transmitting information from the mobiledevice 325 and/or on-board computer 329.

The client application 669 may function as part of a stand-alone systemor as part of a system wherein the front-end components 311 communicatewith back-end components 313 as described with reference to FIG. 3. Theclient application 669 may include machine-readable instruction forimplementing a user interface to allow a user to input commands to, andreceive information from, the driver-evaluation system 100.

One of the plurality of applications 665 may be a native web browser673, such as Apple's Safari®, Google Android™ mobile web browser,Microsoft Internet Explorer® for Mobile, Opera Mobile™, that may beimplemented as a series of machine-readable instructions for receiving,interpreting, and displaying web page information from the server 351 orother back-end components 313 while also receiving inputs from the user.Another application of the plurality of applications may include anembedded web browser 677 that may be implemented as a series ofmachine-readable instructions for receiving, interpreting, anddisplaying web page information from the servers 351 or other back-endcomponents 313 within the client application 669.

One of the plurality of routines may include an image capture routine671 that coordinates with the image capture devices 621, 627 to retrieveimage data for use with one or more of the plurality of applications,such as the client application 669, or for use with other routines.Another routine in the plurality of routines may include anaccelerometer routine 675 that determines the force and direction ofmovements of the mobile device 325 and/or on-board computer 329. Theaccelerometer routine 675 may process data from the accelerometer array629 to determine a vector describing the motion of the mobile device 325and/or on-board computer 329 for use with the client application 669. Insome embodiments where the accelerometer array 629 has X-axis, Y-axis,and Z-axis accelerometers 629 x, y, z, the accelerometer routine 675 maycombine the data from each accelerometer 629 x, y, z to establish avector describing the motion of the mobile device 325 and/or on-boardcomputer 329 through three dimensional space. Furthermore, in someembodiments, the accelerometer routine 675 may use data pertaining toless than three axes, such as when determining when the vehicle 323 isbraking.

A user may launch the client application 669 from the mobile device 325and/or on-board computer 329, to access the server 351 to implement thedriver-evaluation system 100. Additionally, the customer or the user mayalso launch or instantiate any other suitable user interface application(e.g., the native web browser 673, or any other one of the plurality ofsoftware applications 665) to access the server 613 to realize thedriver-evaluation system 100.

The server 613 may further include a number of software applications.The various software applications are responsible for generating thedata content to be included in the web pages sent from the web server373 to the mobile device 325 and/or on-board computer 329. The softwareapplications may be executed on the same computer processor as the webserver application 373, or on different computer processors.

In embodiments where the mobile device 325 and/or on-board computer 329is a thin-client device, the server 351 may perform many of theprocessing functions remotely that would otherwise be performed by themobile device 325 and/or on-board computer 329. In such embodiments, themobile device 325 and/or on-board computer 329 may gather data from itssensors as described herein, but instead of analyzing the data locally,the mobile device 325 and/or on-board computer 329 may send the data tothe server 351 for remote processing. The server 351 may perform theanalysis of the gathered data to evaluate the driving performance of thedriver 321 as described below. If the server 351 determines that thedriver 321 may be impaired, the server 351 may command the mobile device325 and/or on-board computer 329 to alert the driver 321 as describedbelow. Additionally, the server 351 may generate the metrics andsuggestions described below based on the gathered data.

7. An Example Method for Displaying a Report/GUI

FIG. 7 is a flow diagram depicting an example method 700 for displayinga driver evaluation report/GUI, such as the GUI 411 shown in FIG. 4,according to an embodiment.

The method 700 may be implemented by the driver-evaluation system 100shown in FIG. 1B and/or the driver-evaluation system 300 shown in FIG.3. More particularly the method 700 may be performed by: the mobiledevice 325, the on-board computer 329, the server 351, or somecombination thereof. The method 700 may be saved as a set ofinstructions, routines, programs, or modules at computer readable mediafound, for example, in memory devices accessible by thedriver-evaluation system 100. For example, some or all of the method 700may be saved as the progress module 139 described with reference to FIG.1B. While the method 700 is described with reference to thedriver-evaluation system 100 (shown in FIG. 1B), the driving-monitorsystem 30 (shown in FIG. 1B), and the mobile device 325 (shown in FIG. 3and FIG. 6), the method 700 may be implemented according to otherembodiments.

The method 700 may be initiated by a command (block 702). The commandmay be a user command received by the mobile device 325 and/or on-boardcomputer 329 via the client application 669 (shown in FIG. 6).Alternatively or additionally, the command may be sent by the server 351or may be generated automatically by the mobile device 325 and/oron-board computer 329 after the meeting of a condition (e.g., thevehicle 323 has been started; the mobile device 325 is within aspecified distance from the vehicle, a certain time, etc.).

Next, the sensors (e.g., sensors 61, which may include sensors of themobile device 325 and/or of the on-board computer 329) may be calibrated(block 704). For example, a GPS unit, an accelerometers, a compass, agyroscope, an image capture device, and/or other sensors may beactivated and/or calibrated.

For example the front image capture device 621 may attempt to detect theface and eye(s) of the driver 321. Calibration may further entailadjusting the front image capture device 621 to account for the driver's321 skin tone, facial characteristics, etc., ambient light in thevehicle, the background behind the driver 321, etc. The back imagecapture device 627 may also be calibrated, such as, to attempt to detectthe road in front of the vehicle, identify lane markings, and identifyother vehicles on the road. Calibration may further entail adjusting theback image capture device 627 to account for the color of the road, roadconditions (e.g., a wet road from rain or an icy road from snow), thecolor of lane markings, the time of day and ambient light, etc. Theaccelerometer array 629 may also be calibrated. Such calibration mayinclude accounting for constant vibration (e.g., the vibration caused bythe engine of the vehicle 321) or other repetitive forces applied to themobile device 325 and/or on-board computer 329.

After calibration, the mobile device 325 and/or on-board computer 329may begin to collect data about driver performance using the sensor(s)61 (shown in FIG. 1B and FIG. 6) (block 706).

8. Example Methods for Logging a Driving Session

FIGS. 8, 9A, and 9B are flow diagrams depicting example logging methods800 and 900 according to an embodiment. The methods 800 and/or 900 maybe implemented by the driver-evaluation system 100 (shown in FIG. 1) ordriver-evaluation system 300 (shown in FIG. 3) while gathering dataabout driver performance (see, e.g., block 706 shown in FIG. 7). It willbe understood that in some embodiments, one or more of the steps inmethod 800 and/or 900 are not implemented.

8.1. Example Method 800 for Logging Movement-Data and Other Data

Performance indicators may be a series of measurements of conditions orcharacteristics pertaining to driver performance. Accordingly, sensors61 (e.g., the front image capture device 621, back image capture device627, and/or accelerometer array 629) may be used to measure theseconditions and characteristics. Such measurements may be loggedperiodically (e.g., every millisecond, every second, etc.) or may belogged conditionally on the occurrence of an event (e.g., a force of amagnitude above a certain threshold is detected) and stored in datastorage 663 as a performance indicator log. Such performance indicatorlogs may also include a timestamp to note the time of the measurementand/or a location stamp to note the GPS coordinates of the measurement.

The driver-evaluation system 100 may make performance indicator logs forprimary performance indicators such as driver gaze location and vehiclemovement (e.g., vehicle position relative to lane markings, vehicleposition relative to other vehicles; and acceleration along the X, Y, orZ axes). The driver-evaluation system 100 may derive secondaryperformance indicators from the primary performance indicators such as:driver gaze fixation, lane deviation, failure to maintain lanecentering, time to collision, time to brake, time to react, longitudinalvehicle control, vehicle braking, vehicle acceleration, and lateralacceleration. Both the primary performance indicator logs and secondaryperformance indicator logs may be logged separately (e.g., a log forgaze location, a log for X axis force, etc.) or may be logged together.These separate or integrated logs may be stored in data storage 669 ormay be transmitted to the server 351 via the network 341 for remotestorage. In an embodiment, the primary and/or secondary performanceindicators are logged at the performance log 135 shown in FIG. 1B.

-   -   8.1(A) Log GPS Coordinates

In an embodiment, the driver-evaluation system 100 may receive GPScoordinates from a GPS receiver. In particular, the driver-evaluationsystem 100 may include a location stamp for each performance log thatmay be recorded by taking a reading from the GPS unit 623 (which may beincluded in the mobile device 325, the on-board computer 329, or anotherdevice) to determine current location of the vehicle 321 (block 802). Asdiscussed above, a location stamp may be recorded for each performancelog. Accordingly, it may be advantageous to take a reading from the GPSunit 623 prior to recording any performance log. Additionally, with aseries of GPS location logs, the velocity of the vehicle 321 may bedetermined. Further, if speed limit data about the route taken isavailable, a series of GPS location logs and a calculated velocity maybe used to make a determination about whether the driver 321 ismaintaining a speed above a minimum speed limit and/or below a maximumspeed limit. In some embodiments, GPS coordinates are not collected.

-   -   8.1(B) Log Gaze Location

In an embodiment, driver gaze location may be determined by monitoringthe eye or eyes of driver 321 with the front image capture device 621(block 804). Driver gaze location may be logged as the horizontal andvertical coordinates of the driver's apparent gaze. Driver gaze locationmay be used to determine when the driver 321 is looking at the road,mirrors, the dashboard, stereo or air conditioning controls, a mobiledevice, etc. In some embodiments, the client application 669 may logwhether the driver 321 is looking at a distraction (e.g., the stereo) orin the direction of an important area for vehicle operation (e.g., theroad, mirrors, etc.).

The driver-evaluation system 100 may differentiate between the importantareas for vehicle operation in gaze location logs. The driver-evaluationsystem 100 may include a first value in the gaze location log indicatingthat the driver was looking at the road, a second value in the gazelocation log indicating that the driver was looking at the rear viewmirror, a third value in the gaze location log indicating that thedriver was looking at the left side mirror, a fourth value in the gazelocation log indicating that the driver was looking at the right sidemirror, and a fifth value in the gaze location log indicating that thevehicle was looking at the dashboard gauges (e.g., speedometer). Theclient application 669 may also include a timestamp and/or locationstamp in the gaze location log. If a gaze location log is made everytime the driver starts looking at a different object, then the durationof a particular driver gaze can be determined by the difference betweenthe time the driver 321 began looking at the object and the time thedriver 321 begins looking at another object. In some embodiments drivergaze location is not determined.

-   -   8.1(C) Log Vehicle Position

The back image capture device 627 may be used to monitor conditions onthe road including identifying lane markings and/or other vehicles onthe road. Vehicle position relative to lane markings may be determinedby processing an image or series of images captured by the back imagecapture device 627 to determine the distance of the vehicle 321 fromlane markings on either or both sides of the vehicle 321 (block 806).The mobile device 325 and/or on-board computer 329 may determine vehicleposition relative to lane markings regularly with a timestamp and/orlocation stamp and store the log of vehicle position relative to lanemarkings in data storage 669 or send the log of vehicle positionrelative to lane markings to the server 351 for remote storage.

Similarly, vehicle position relative to other vehicles (also referred toas vehicle headway distance) may be determined by processing an image orseries of images captured by the back image capture device 627 todetermine the distance of the vehicle 321 from other vehicles on theroad in front of the vehicle 321 (block 808). For example, the imagescaptured by the back image capture device 627 may be analyzed to comparethe visual area of an object in front of the vehicle in one or moreimages (i.e., if the visual area is larger in a first image relative toa second image, the object was likely closer at the time the secondimage was captured whereas if the visual area of the object is smallerin a first image relative to a second image, the object was likelyfurther away at the time the second image was captured) and/or thevisual area of the road between the vehicle 321 and an object (i.e., ifthe visual area of the road is larger in a first image relative to asecond image, the object was likely further away at the time the secondimage was captured whereas if the visual area of the road is smaller ina first image relative to a second image, the object was likely closerat the time the second image was captured). Additionally oralternatively, if the back image capture device 627 is properlycalibrated, a single image of the road ahead of the vehicle may besufficient to estimate the distance of the vehicle 321 from the vehicleahead using known trigonometric principles. The mobile device 325 and/oron-board computer 329 may determine vehicle position relative to othervehicles regularly with a timestamp and store the log in data storage669 or send the log to the server 351 for remote storage. Additionally,information from the GPS unit 623 may be incorporated into the log toadd information about the current velocity and/or location of thevehicle 321.

-   -   8.1(D) Log Movement-Data

The accelerometer array 629 may be used to monitor forces on the vehiclein the X, Y, and/or Z axis and create accelerometer logs (block 810). Insome embodiments, the Y-axis may be oriented along left to right axis ofthe mobile device 325 and/or on-board computer 329, the Z-axis may beoriented along the top to bottom axis of the mobile device 325 and/oron-board computer 329, and the X-axis may be oriented along the front toback axis of the mobile device 325 and/or on-board computer 329.However, the axes could be oriented in any number of ways. The mobiledevice 325 and/or on-board computer 329 may determine the magnitude of aforce along one of the axes and make an accelerometer log with atimestamp and/or location stamp in data storage 669 or send theaccelerometer log to the server 351 for remote storage.

-   -   8.1(E) Receive User Input

In an embodiment, the user input device 633 may be used to collectcomments from the driving instructor during the driving session (block812). By activating a control, a user may create a comment or note aboutthe driving session. The user may record an audible comment or type atextual comment. For example, a driving instructor may make a commentafter instances of poor driving performance such as the driver 321stopping in a crosswalk, crossing the center line of the street,applying the brakes too late, etc. The driving instructor may also makecomments after instances of good driving performance such as awell-executed turn. The comments may be related to a particular action(e.g., a particularly well executed turn) or general comments about thedriving session (e.g., “Sam has shown a marked improvement since thesession last week.”). The instructor may make notes during and/or afterthe driving session. Comments may be entered by the instructor directlyon the first mobile device 325 and/or on-board computer 329 performingthe driver performance evaluation methods discussed herein, or commentsmay be entered via a second mobile device 325 in communication with thefirst mobile device 325 and/or on-board computer 329. For example, thedriving instructor may use a tablet computer to record comments whichare relayed to the first mobile device 325 and/or on-board computer 329via Bluetooth® or Near Field Communication or any known short-rangenetworking technique. Alternatively, the second mobile device 325 maycommunicate with the first mobile device 325 and/or on-board computer329 via the network 341. The comments may be stored with a timestampand/or location stamp in data storage 669 or sent to the server 351 forremote storage

If the driver session has concluded, the logging method 800 may end.However if the student driving session has not concluded, the primaryperformance indicator logging method 400 may continue to gather data(block 414).

8.2. Example Method 900 for Logging Performance Indicators

In an embodiment, secondary performance indicators may be determined andlogged based on an analysis of primary performance indicators. Forexample, movement of the driver 321 may be determined from movement-datareceived from sensors 61, and may be analyzed to identify safe or unsafemovements, for example. These unsafe movements may be logged assecondary performance indicators. Secondary performance indicators mayinclude gaze fixation, lane deviation and/or centering,time-to-collision metrics, hard braking events, hard accelerationevents, and/or vehicle swerving.

-   -   8.2(A) Gaze Fixation

Referring to FIG. 9A, driver gaze fixation may be determined byanalyzing a set of driver gaze location logs and determining the lengthof time in which the driver 321 is looking at a particular place (block902). It will be understood that when looking at a particular place, adriver 321 may move his or her eyes slightly. Such minor variations maybe disregarded subject to a sensitivity setting.

Driver gaze fixation records instances where a driver has looked at thesame object for more than a threshold period of time (e.g., 100 ms)(block 904). For example, driver gaze fixation may be used to detectwhen the driver 321 has his or her gaze fixed on the road above athreshold level (e.g., the driver 321 has not looked at mirrors ordashboard in more than two seconds). Additionally or alternatively,driver gaze fixation may be determined by analyzing a set of driver gazelocation logs and determining the eye movement of the driver 321 bycalculating the degree to which the driver's 321 eyes have moved in afirst image relative to a second image. When employing such an eyemovement velocity-based gaze detection algorithm, driver gaze fixationmay record instances where the velocity of eye movement is below athreshold value (e.g., thirty-five degrees per second).

If driver gaze fixation is detected, the client application 669 may makea gaze fixation log with a timestamp and/or location stamp (block 906).

-   -   8.2(B) Lane Deviation

With the logs of vehicle position relative to lane markings, lanedeviation may be determined by analyzing the logs of vehicle positionrelative to lane markings to determine when the distance between a lanemarking and vehicle 321 indicates that the vehicle 321 has changed lanes(block 908). While lane changes are a normal aspect of vehicleoperation, a slow lane change may indicate that the operator 106 is notproperly controlling the vehicle 321 and/or is distracted.

Accordingly, the driver-evaluation system 100 may analyze the log ofvehicle position relative to lane markings to detect lane changes thatoccur over a period of time greater than a threshold value (e.g., twentyseconds, thirty seconds, etc.) (block 910).

When a slow lane deviation is detected, the client application may makea slow lane deviation log with a timestamp and/or location stamp (block912).

-   -   8.2(C) Lane Centering

With the logs of vehicle position relative to lane markings, failure tomaintain lane centering may be determined by analyzing the logs ofvehicle position relative to lane markings to determine when thedistance between a lane marking and vehicle 321 indicates that thevehicle 321 is not centered in the lane (block 914). Similarly to lanedeviation, if a vehicle 321 starts to veer from the center of the laneover a long period of time, this may indicate that the driver 321 is notproperly controlling the vehicle 321 and/or is distracted.

Accordingly, the driver-evaluation system 100 may analyze the log ofvehicle position relative to lane markings to detect an increasingfailure to maintain lane centering that occurs over a period of timegreater than a threshold value (e.g., fifteen seconds) (block 916).

When a failure to maintain lane centering is detected, the clientapplication 669 may make a log with a timestamp and/or location stamp(block 918).

-   -   8.2(D) Time-to-Collision

Referring now to FIG. 9B, with the logs of vehicle position relative toother vehicles, time to collision may be determined by analyzing thelogs of vehicle position relative to other vehicles to determine when adecreasing time to collision indicates that the vehicle 321 may be tooclose behind another vehicle (block 920). Time to collision may becalculated in a number of ways (e.g., by dividing the distance betweenthe vehicle 321 and the vehicle ahead by the difference in velocitybetween the two vehicles, etc.).

For example, the client application 669 may determine the visual area ofan object in front of the vehicle 321 in a first image, determine thevisual area of the object in a second image, and calculate thedifference between the two areas. Then, the time to collision may beestimated by noting the change in the difference between the two areasrelative to the amount of time between the first time and the secondtime. Additionally or alternatively, the client application 669 maydetermine the visual area of the road in front of the vehicle 321 in afirst image, determine the visual area of the road in a second image,and calculate the difference between the two areas. Then, the time tocollision may be estimated by noting the change in the differencebetween the two areas relative to the amount of time between the firsttime and the second time. Alternatively, the distance between thevehicle 321 and the vehicle ahead may be calculated with a single imageusing trigonometry as discussed above. Input from the GPS unit 623 maybe used to determine current velocity of the vehicle 321.

The driver-evaluation system 100 may analyze the log of vehicle positionrelative to other vehicles to detect when time to collision decreasesbelow a threshold value (e.g., 2 second etc.), which may indicate, forexample, that the driver 321 is tailgating the vehicle ahead (block920).

When a below threshold time to collision is detected, the clientapplication 669 may make a time to collision below threshold log with atimestamp and/or location stamp (block 922). Alternatively oradditionally, the data used to calculate time to collision may also beused to calculate similar metrics such as time to brake (i.e., theamount of time the driver 321 has to apply the brakes in order toprevent collision with an object) and/or time to react (i.e., the amountof time a driver 321 has to recognize an imminent collision and react toprevent it by swerving and/or applying the brakes).

In addition to the data used to calculate time to collision, it may beadvantageous to incorporate additional data into the calculation of timeto brake and time to react such as the stopping capability of thevehicle 321, road conditions (e.g., wet, icy, unpaved, etc.), and thereaction time of the driver 321 (e.g., determined by a test performed onthe individual driver 321, calculated by adjusting average humanreaction time to account for the driver's 321 age, health, performancelevel as determined herein, etc.). As with time to collision, time tobrake and/or time to react may be compared to a threshold time and usedto generate a performance log.

-   -   8.2(E) Hard Braking

With the accelerometer logs, vehicle braking or deceleration may bemonitored by noting deceleration sensed by an accelerometer oriented inthe fore-aft direction of the vehicle (i.e., the X-axis) (block 926). Ifthe force measured by the accelerometer array 629 indicates that thebrakes of the vehicle 321 have been applied sharply (e.g., the forcemeasured in the X-axis exceeds a threshold value) (block 928), theclient application 669 may make a hard brake log with a timestamp and/orlocation stamp (block 930).

-   -   8.2(F) Aggressive Acceleration

With the accelerometer logs, vehicle acceleration may be monitored bynoting acceleration sensed by an accelerometer oriented in the fore-aftdirection of the vehicle (i.e., the X-axis) (block 932). If the forcemeasured by the accelerometer array 629 indicates that the acceleratorof the vehicle 321 has been applied sharply (e.g., the force measured inthe X-axis exceeds a threshold value) (block 934), the clientapplication 669 may make a sharp acceleration log with a timestampand/or location stamp (block 936).

-   -   8.2(G) Swerving

With the accelerometer logs, vehicle lateral acceleration may bemonitored by analyzing forces measured by an accelerometer orientedalong the left to right side of the vehicle 321 (i.e., the Y-axis)(block 938). If the force measured by the accelerometer array 629indicates that the vehicle 321 has swerved (e.g., the force measured inthe Y-axis exceeds a threshold value) (block 940), the clientapplication 669 may make a swerve log with a timestamp and/or locationstamp (block 942).

In embodiments where the mobile device 325 and/or on-board computer 329is a thin client device, the mobile device 325 and/or on-board computer329 may send the logs to the server 351 soon after logging the recordedinformation. In such embodiments, the server 351 may analyze the logs ofprimary performance indicators as discussed above to determine secondaryperformance indicators.

Referring again to FIG. 7, after gathering primary and secondaryperformance indicators, the driver-evaluation system 100 may analyze theprimary and secondary performance indicators to generate one or morereports or GUIs about the driving session (see, e.g., block 708 shown inFIG. 7).

Generating the one or more reports or GUIs may include generatingindividual skill performance score(s) for the driving session for one ormore of a gaze location score, a scanning frequency score, a gazelocation score, a lane deviation score, a lane centering score, a timeto collision score, a braking score, an acceleration score, or asteering score. Additionally or alternatively, the report or GUI mayinclude one or more composite score(s) calculated using the individualskill performance score(s) that were generated. FIGS. 10 and 11 describeexamples of how various individual skill performance scores andcomposite scores may be generated in exemplary embodiments.

Further, the report(s) or GUI(s) generated may include a recitation ofimportant events that occurred during the driving session such asbraking, acceleration, and/or swerving with forces exceeding a safetythreshold (e.g., a hard brake at the intersection of Clark St. andDivision St., a hard right turn at the intersections of LaSalle St. andOhio St., etc.) with a timestamp and/or location stamp. The report mayalso include any comments made by the driving instructor during andafter the driving session. It may be advantageous to represent theseimportant events and comments visually on a map.

After the report(s)/GUI(s) have been generated, they may be distributedand/or displayed (see, e.g., block 710 shown in FIG. 7). The report(s)may be distributed via email or other type of electronic messaging tothe driving instructor, the driver, and/or the parents of the driver.The report(s)/GUI(s) may also be displayed on a display of the mobiledevice 325 and/or on-board computer 329 or any other computing devicebeing used by one or more of the driver, parents, and drivinginstructor. Additionally, it may be advantageous to prepare a printedversion of the report(s) and/or generate automated voicemail messages,and using known techniques.

9. Example Methods for Score Calculation

FIG. 10 illustrates an example method 1000 for calculating a drivingscore according to an embodiment. FIG. 11 depicts an example method 1100for calculating a driver scanning score according to an embodiment. Themethods 1000 and 1100 may be implemented, in whole or in part, by thedriver-evaluation system 100 (shown in FIG. 1B), the driving-monitorsystem 30 (shown in FIG. 1B), the driver-evaluation system 300 (shown inFIG. 3), and/or the driving-monitor system 330 (shown in FIG. 3). Thus,it will be understood that while the methods 1000 and 1100 are generallydescribed with reference to the driver-evaluation system 100 and thedriving-monitor system 30, the methods 1000 and 1100 may also beimplemented by the driver-evaluation system 300 and the driving-monitorsystem 330.

The methods 1000 and 1100 may be saved as a set of instructions,routines, programs, or modules at computer readable media found, forexample, in memory devices accessible by the driver-evaluation system100. For example, some or all of the methods 1000 and/or 1100 may besaved as the progress module 139 described with reference to FIG. 1B. Inan embodiment, the methods 1000 and/or 1100 may be saved, in whole or inpart, as a module distinct from the progress module 139.

9.1. Method 1000 for Calculating a Driving Score

In an embodiment, the method driver-evaluation system 100 begins when anacceleration score is determined (block 1002). For example, thedriving-monitor system 30 may determine an acceleration score using oneor more performance logs 135. As an example, an acceleration score maybe determined by subtracting points from a total score of 100 every timea driver applies too much acceleration during the driving session. Thenumber of points subtracted may be determined according to a series ofthreshold values. For example, 1 point may be subtracted for a “hard”acceleration (e.g., acceleration above threshold A1 m/s²), 2 points maybe subtracted for a “very hard” acceleration (e.g., acceleration abovethreshold A2 m/s²), and 3 points may be subtracted for a “severe”acceleration (e.g., acceleration above threshold A3 m/s²).

In an embodiment, a braking score may also be determined (block 1004).For example, the driving-monitor system 30 may generate or determine abraking score using one or more performance logs 135. A braking scoremay be determined by subtracting points from a total score of 100 everytime the driver 321 applies too much braking (or deceleration) duringthe driving session. The number of points subtracted may be determinedaccording to a series of threshold values. For example, 1 point may besubtracted for a “hard” braking (e.g., braking above threshold B1 m/s²),2 points may be subtracted for a “very hard” braking (e.g., brakingabove threshold B2 m/s²), and 3 points may be subtracted for a “severe”braking (e.g., braking above threshold B3 m/s²).

Further, in an embodiment a steering score may be determined (block1006). For example, the driving-monitor system 30 may determine asteering score using one or more performance logs 135. The number ofpoints subtracted may be determined according to a series of thresholdvalues. For example, 1 point may be subtracted for a “hard” turning(e.g., turning above threshold T1 m/s²), 2 points may be subtracted fora “very hard” turning (e.g., turning above threshold T2 m/s²), and 3points may be subtracted for a “severe” turning (e.g., turning abovethreshold T3 m/s²). Of course, it will be understood that for each scoredifferent numbers of points may be subtracted and different units may beused. Further, it will also be understood that the scores may becalculated using methods other than subtraction from 100 such as addingpoints to a store for every acceleration, brake, and/or turn that doesexceed the thresholds discussed above.

After determining various scores or sub-scores (e.g., for acceleration,braking, and steering as discussed above) weighting factors may beapplied (blocks 1008 a-1008 c). In particular, the driving-monitorsystem 30 may multiply each score by a weighting factor. For example, ifeach score is weighted equally, the weighting factors may all be .333.However, it may be advantageous to weight one score higher than another.For example, sharp acceleration may be less important than braking andsteering in evaluating the performance of the driver. In such anembodiment, the weighting factors may be 0.25, 0.35, and 0.40,respectively. In some embodiments, the weighting factors may be adjustedbased on previous data for the user or for a large group of users. Theweighting factors may be adjusted by one of the many known learningalgorithms such as a support vector machine (SVM).

The driving-monitor system 30 may sum the weighted scores to determine acomposite driving session score (block 1010). The composite drivingsession score may be logged in with a timestamp and stored to memory(e.g., the memory 133 shown in FIG. 1B) and/or sent to the server 351for remote storage. Alternatively, it will be understood that instead ofa weighted sum adding up to a composite driving session score, theclient application 669 may instead be a weighted sum that is subtractedfrom a maximum composite driving session score.

In an embodiment, the composite driving session score is determined, atleast in part, based on other scores instead of or in addition to thescores described above. For example, the composite driving session scoremay be determined, at least in part, based on a driver scanning score(described with reference to FIG. 11).

While the exemplary embodiment discussed above uses a 100 point scale,it will be appreciated that a 100 point scale is just one of many pointscales that could be used (e.g., 50 point scale, 200 point scale, 500point scale, 1000 point scale, etc.). Additional primary and secondaryperformance indicators may be used in the determination of the compositedriving session score. For example, a gaze location score, a scanningfrequency score, a gaze location score, a lane deviation score, a lanecentering score, or a time to collision score may be added to thecalculation of the composite driving session score. Each primary andsecondary performance indicator may be used to generate a respectivescore similar to the scores described in connection to FIG. 10.

For example, a respective score for each may be calculated bysubtracting 1 point from a total score of 100 for every instance of agaze fixation, slow lane deviation, failure to maintain lane centering,below threshold time to collision, respectively. Once a score for someor all of the gaze fixation, slow lane deviation, failure to maintainlane centering, below threshold time to collision performance has beencalculated, scores may be added to the weighted sum discussed above. Itwill be appreciated that when additional scores are added to theweighted sum, it may be advantageous to change the weighting coefficientfor some or all of the other scores in the weighted sum. Additionally,the driving-monitor system 100 may be configurable to adjustsensitivity, change point deduction values, etc.

9.2. Method 1100 for Calculating a Driver Scanning Score

In an embodiment, the method 1100 begins when a gaze locationdistribution is calculated (block 1102). In particular, thedriving-monitor system 30 may determine a gaze location distributionusing the gaze locations logs (which may, e.g., be saved as part of theperformance log(s) 135 shown in FIG. 1B). Because each gaze location logmay include geographic coordinates corresponding to where the driver 321was looking at a particular time during the driving session, it may beadvantageous to group the gaze location logs according to theircoordinates. For example, it is likely that many gaze location logs weremade when the driver 321 was looking at one of the mirrors or the roadahead. Thus, even without knowledge of the interior layout of thevehicle 321, the method 1100 may enable the driver-evaluation system 100to determine where important features of the vehicle 321 are locatedbased on the statistical distribution of gazes. A significant number ofgazes to the far right may correspond to the right side mirror, asignificant number of gazes to the upper center may correspond to therear view mirror, etc. Accordingly, the method 1100 may enable thedriver-evaluation system 100 to sort the gaze location logs into groupsfor right side mirror gazes, left side mirror gazes, rear mirror gazes,road gazes, and other gazes. The driver-evaluation system 100 mayimplement the method 1100 to total the amount of time the driver 321 waslooking at each location and determine an average amount of time theeyes of the driver 321 were not focused on the road ahead.

Using the gaze location distribution, a mirror checking score may becalculated (block 1104). The mirror checking score may be determined(e.g., by the driver-evaluation system 100) by comparing the amount oftime during the driving session that the driver 321 spent gazing at theright side mirror, left side mirror, and rear view mirror to an expectedamount of time. The expected amount of time may be a threshold levelestablished by, for example, observing good drivers to determine howoften each of the good drivers gaze at each mirror over a period of time(e.g., looking at each mirror for 0.5 second every 30 seconds). Themirror checking score may be calculated by subtracting points from 100every time the driver 321 fails to look at each mirror periodically atthe expected amount during the driving session. Alternatively, using adataset of driving performances by a large number of drivers (e.g.,other drivers that have used the systems and methods described herein inthe past), the driver-evaluation system 100 may calculate a distributionof mirror checking performance. Using this distribution, the method 1100may calculate in which percentile the performance of the driver 321belongs, and store that percentile as the mirror checking score.

In an embodiment, a gaze fixation score may be calculated (block 1106).The gaze fixation score may be determined (e.g., by thedriver-evaluation system 100) by subtracting 1 point from a total scoreof 100 every time gaze fixation is detected during a certain period oftime. As with the mirror checking score discussed above, using a datasetof driving performances by a large number of drivers (e.g., otherdrivers that have used the systems and methods described herein in thepast), the driver-evaluation system 100 may calculate a distribution ofgaze fixation performance. Using this distribution, thedriver-evaluation system 100 may implement the method 1100 to calculatein which percentile the performance of the driver 321 belongs, and storethat percentile as the gaze fixation score.

In some embodiments, a scanning frequency score may be calculated (e.g.,by the driver-evaluation system 100) (block 1108). The scanningfrequency score may be calculated using one or more performance logs135. A scanning frequency score can be determined by subtracting 1 pointfrom a total score of 100 every time the driver 321 fails to shift hisor her gaze from one important area for vehicle operation (e.g., theroad, mirrors, etc.) to another important area for vehicle operationwithin a threshold period of time (e.g., 5 seconds) within a certainperiod of time. For example, a driver 321 who is distracted may not lookfrom the road to check the mirrors and speed indicator with sufficientfrequency. As with the mirror checking score discussed above, using adataset of driving performances by a large number of drivers (e.g.,other drivers that have used the systems and methods described herein inthe past), the driver-evaluation system 100 may calculate a distributionof scanning frequency performance. Using this distribution, thedriver-evaluation system 100 may implement the method 1100 to calculatein which percentile the performance of the driver 321 belongs, and storethat percentile as the scanning frequency score. Each score may belogged in with a timestamp and stored, e.g., in data storage at themobile device 325 or on-board computer 329, and/or sent to the server351 for remote storage.

10. Additional Considerations

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

10.1. Network(s)

As used herein, unless otherwise specified, the term “network” is acollection of nodes (e.g., devices or systems capable of sending,receiving and/or forwarding information) and links which are connectedso as to enable telecommunication between the nodes.

Generally speaking, the term “node” refers to a connection point,redistribution point, or a communication endpoint. A node may be anydevice or system (e.g., a computer system) capable of sending, receivingand/or forwarding information. For example, end systems that originateand/or ultimately receive a message are nodes. Intermediary device thatreceive and forward the message are also generally considered to be“nodes.”

A “link” is a pathway or medium connecting two or more nodes. A link maybe a physical link and/or a logical link. A physical link is theinterface and/or medium(s) over which information is transferred, andmay be wired or wireless in nature. Examples of physicals links mayinclude a cable with a conductor for transmission of electrical energy,a fiber optic connection for transmission of light, and/or a wirelesselectromagnetic signal that carries information via changes made to oneor more properties of an electromagnetic wave(s).

A logical link between two or more nodes represents an abstraction ofthe underlying physical links and/or intermediary nodes connecting thetwo or more nodes. For example, two or more nodes may be logicallycoupled via a logical link. The logical link may be established via anycombination of physical links and intermediary nodes (e.g., routers,switches, or other networking equipment).

A link is sometimes referred to as communication channel. In particular,in a wireless communication system a channel generally refers to aparticular frequency or frequency band. A carrier signal (or carrierwave) is transmitted at the particular frequency or within theparticular frequency band of the channel. In some instances, multiplesignals may be transmitted over a single band/channel. For example,signals may sometimes be simultaneously transmitted over a singleband/channel via different sub-bands or sub-channels. As anotherexample, signals may sometimes be transmitted via the same band byallocating time slots over which respective transmitters and receiversuse the band in question.

As already noted, a network is a collection of nodes and links. Anetwork may include dedicated routers responsible for directing trafficbetween nodes, and, optionally, dedicated devices responsible forconfiguring and managing the network. Some or all of the nodes may bealso adapted to function as routers in order to direct traffic sentbetween other network devices. Network devices may be inter-connected ina wired or wireless manner, and network devices may have differentrouting and transfer capabilities. For example, dedicated routers may becapable of high volume transmissions while some nodes may be capable ofsending and receiving relatively little traffic over the same period oftime. Additionally, the connections between nodes on a network may havedifferent throughput capabilities and different attenuationcharacteristics. A fiberoptic cable, for example, may be capable ofproviding a bandwidth several orders of magnitude higher than a wirelesslink because of the difference in the inherent physical limitations ofthe medium. A network may include networks or subnetworks, such as alocal area network (LAN) or a wide area network (WAN).

10.2. Communication Interface(s)

Some of the devices and systems described herein include a“communication interface” (sometimes referred to as a “networkinterface”). A communication interface of a system enables the system tosend information to other system and/or receive information from othersystems. In some instances, a communication interface of a system may beutilized to establish a direct connection to another system. In someinstances, a communication interface of a system enables the system toconnect to a network (via a link).

To illustrate, a communication interface can include circuitry forpermitting wireless communication (e.g., short-range and/or long-rangecommunication) with one or more devices or systems using any suitablecommunications protocol. For example, a communication interface maysupport Wi-Fi (e.g., an 802.11 protocol), Ethernet, Bluetooth, highfrequency systems (e.g., 900 MHZ, 2.4 GHZ, and 5.6 GHZ communicationsystems), infrared, transmission control protocol/internet protocol(“TCP/IP”) (e. g., any of the protocols used in each of the TCP/IPlayers), hypertext transfer protocol (“HTTP”), BitTorrent, file transferprotocol (“FTP”), real-time transport protocol (“RTP”), real-timestreaming protocol (“RTSP”), secure shell protocol (“SSH”), any othercommunications protocol, or any combination thereof. A communicationinterface of a system may also include circuitry that enables the systemto be electrically coupled to another device and communicate with thatother device.

10.3. Hardware and Software System(s)/Module(s)

Additionally, certain embodiments are described herein as includinglogic or a number of routines, subroutines, applications, orinstructions. These may constitute either software (e.g., code embodiedon a machine-readable medium) or hardware. In hardware, the routines,etc., are tangible units capable of performing certain operations andmay be configured or arranged in a certain manner. In exampleembodiments, one or more computer systems (e.g., a standalone, client orserver computer system) or one or more hardwaremodules/systems/subsystems of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware module that operates to performcertain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

10.4. Processor(s)

The various operations of example methods described herein may beperformed, at least partially, by one or more processors. Suchprocessors may be configured to fetch and execute instructions stored tomemory. By executing these instructions, the processor can carry outvarious operations or functions.

The processors may be temporarily configured (e.g., by instructions orsoftware) or permanently configured to perform the relevant operations.Whether temporarily or permanently configured, such processors mayconstitute processor-implemented modules that operate to perform one ormore operations or functions. The modules referred to herein may, insome example embodiments, comprise processor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or more processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

10.5. Memory and Computer-Readable Media

Generally speaking, as used herein the phrase “memory device” may referto any system or device including computer-readable media (“CRM”), whichmay be any available media accessible by the relevant computing systemfor placing, keeping, and/or retrieving information (e.g., data,computer-readable instructions, program modules, etc). The CRM may beimplemented in any technology, device, or group of devices included inthe relevant computing system or in communication with the relevantcomputing system. The CRM may include both volatile and nonvolatilemedia, and removable and non-removable media. The CRM may include, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore information and which can be accessed by the computing system. TheCRM may be communicatively coupled to a system bus, enablingcommunication between the CRM and other systems or components coupled tothe system bus. In some implementations the CRM may be coupled to thesystem bus via a memory interface (e.g., a memory controller). A memoryinterface is a circuit that manages the flow of data between the CRM andthe system bus.

10.6. System Bus(es)

Generally speaking, a processor or a particular system or subsystem maycommunicate with other components of the system or subsystem via one ormore communication links. When communicating with components in a sharedhousing, for example, the processor may be communicatively connected tothe components by a system bus. Unless stated otherwise, as used hereinthe phrase “system bus” refers to: a data bus (for carrying data), anaddress bus (for determining where the data should be sent), a controlbus (for determining the operation to execute), or some combinationthereof. Further, “system bus” may refer to any of several types of busstructures including a memory bus or memory controller, a peripheralbus, or a local bus using any of a variety of bus architectures. By wayof example, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)local bus, and Peripheral Component Interconnect (PCI) bus also known asMezzanine bus.

10.7. Data/Information Generation and Manipulation

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

10.8. Embodiments

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.

10.9. Relational and Logical Expressions

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the description. Thisdescription, and the claims that follow, should be read to include oneor at least one and the singular also includes the plural unless it isobvious that it is meant otherwise.

Although this detailed description contemplates various embodiments, itshould be understood that the legal scope of the invention is defined bythe words of the claims set forth at the end of this patent. Thisdetailed description is to be construed as exemplary only and does notdescribe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One could implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this patent, which mayfall within the scope of the claims.

It should also be understood that, unless a term is expressly defined inthis patent using the sentence “As used herein, the term ‘______’ ishereby defined to mean . . . ” or a similar sentence, there is no intentto limit the meaning of that term, either expressly or by implication,beyond its plain or ordinary meaning, and such term should not beinterpreted to be limited in scope based on any statement made in anysection of this patent (other than the language of the claims). To theextent that any term recited in the claims of this patent is referred toin this patent in a manner consistent with a single meaning, that isdone for sake of clarity only so as to not confuse the reader, and it isnot intended that such claim term be limited, by implication orotherwise, to that single meaning.

What is claimed:
 1. A driver evaluation system for evaluating progressof a driver's skill level, the driver evaluation system comprising: (A)a driving-monitor system including: (i) a GPS unit or an accelerometerthat generates movement-data based upon a detected movement of avehicle; (ii) a processor that: (a) generates, based upon the generatedmovement-data, a first driving skill score for a driver for a firstdriving session; and (b) generates a progress score for the firstdriving session based upon a comparison between the generated firstdriving skill score for the driver and a second, past driving skillscore for a second, past driving session for the driver; and (B) adisplay device, communicatively connected to the driving-monitor system,that displays a graphic indication to visually indicate a trend,represented by the generated progress score, from the second, pastdriving skill score to the generated first driving skill score.
 2. Thedriver evaluation system of claim 1, further comprising a first housingfor the display device, and a second housing for the driving-monitorsystem.
 3. The driver evaluation system of claim 2, wherein the displaydevice and the driving-monitor system are communicatively connected viaa wireless link.
 4. The driver evaluation system of claim 2, wherein thefirst housing is installed in a dash of the vehicle, the first housingconfigured to house the display device so that a visual output of thedisplay device is observable from within a cabin of the vehicle; whereinthe display device is (i) communicatively connected to a multimediasystem installed in the vehicle, and (ii) configured to receive adisplay input signal from the multimedia system; and wherein themultimedia system receives, from the driving-monitor system, datarepresenting the graphic indication and transmits, to the displaydevice, the data representing the graphic indication.
 5. The driverevaluation system of claim 1, wherein the display device and thedriving-monitor system share a housing, the display device disposedwithin, or on, the housing so that a visual output of the display deviceis observable from outside of the housing.
 6. The driver evaluationsystem of claim 1, wherein a one of the GPS unit or the accelerometerincluded in the driving-monitor system shares a housing with thedriving-monitor system.
 7. The driver evaluation system of claim 1,wherein the display device is a touch display, and wherein the displaydevice displays the graphic indication in response to touch input.
 8. Acomputer-implemented method for evaluation progress of a driver's skilllevel, the method comprising: receiving, at a driving-monitor computersystem, movement-data detected by a GPS unit or by an accelerometer, themovement-data representing detected movement of a vehicle during adriving session; generating, by the driving-monitor computer system andbased upon the received movement-data, a first driving skill score forthe driving session; generating, by the driving-monitor computer system,a progress score for the first driving session based upon a comparisonbetween the generated first driving skill score for a driver and asecond, past driving skill score for a second, past driving session forthe driver; and displaying, by the display device, a graphic indicationto visually indicate a trend, represented by the generated progressscore, from the second, past driving skill score to the generated firstdriving skill score.
 9. The computer-implemented method of claim 8,wherein displaying the graphic indication comprises displaying a binaryindication indicating an improvement or a regression.
 10. Thecomputer-implemented method of claim 9, wherein displaying the graphicindication comprises displaying an upward arrow to indicate theimprovement or displaying a downward arrow to indicate the regression.11. The computer-implemented method of claim 8, wherein displaying thegraphic indication comprises displaying a percentage indicating apercent improvement or a percent regression.
 12. Thecomputer-implemented method of claim 8, wherein displaying the graphicindication comprises displaying a first color when the progress scoreindicates an improvement, and displaying a second color when theprogress score indicates a regression.
 13. A driver evaluation system,the driver evaluation system comprising: a means for generatingmovement-data, the movement-data representing detected movement of avehicle during a driving session; a means for generating, based upon themovement-data, a first driving skill score for a driver for the drivingsession; a means for generating a progress score for the driving sessionbased upon a comparison between the generated first driving skill scorefor the driver and a second, past driving skill score for a second, pastdriving session for the driver; and a means for displaying a graphicindication to visually indicate a trend, represented by the generatedprogress score, from the second, past driving skill score to thegenerated first driving skill score.
 14. The driver evaluation system ofclaim 13, wherein the graphic indication is a bar including a firstmarker and a second marker, wherein the first marker is a graphicindication of the generated first driving skill score, and the secondmarker is a graphic indication of the second, past driving skill score;and wherein a distance between the first marker and the second markerrepresents the trend from the second driving skill score to thegenerated first driving skill score.
 15. The driver evaluation system ofclaim 13, further including: a means to receive user input; a means toidentify the driver based upon the user input; and a means forretrieving, based on the user input, the second, past driving skillscore.
 16. The driver evaluation system of claim 13, further including:a means to receive user input; and wherein the means for displaying thegraphic indication is configured to display the graphic indication inresponse to a user input.
 17. The driver evaluation system of claim 13,wherein the means for displaying the graphic indication comprises aprojector.
 18. The driver evaluation system of claim 13, wherein themeans for displaying the graphic indication comprises a heads-up displayfor the vehicle.